%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Roles and responsabilities of each team}
\label{sec:rr_teams}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\indent Here we discuss responsibilities and roles of each team for
nowadays. How do they participate in our project?

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{Validate information}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\indent The information collected from key users is recent, but often
they are not able to supply technical details. That's why we need to
validate and complete application descriptive with \MIS{}' support
teams. In \tsf{MARS Inc.} users use \tsf{Lotus Notes}, integrated
desktop client option for accessing business e-mail, calendars and
applications on IBM Lotus Domino server.

Majority of \MIS{} teams are using Lotus Notes to have databases
(knowledge database - ref. ITIL) of applications that they are
supporting. Some times these bases are completed with schemas, done in
\tsf{MS Power Point}, which represents relations between applications. Some
of them are limited to have only \tsf{Excel} files where they stock
information about applications. Sometimes, support teams couldn't give
us the information about last changes, because even their databases
are not always updated, they have not good co-ordination with other
teams. This databases or files don't give the possibility for good
communication. So to centralise this database and to have responsible
and accountable persons for data updating was a good idea.

Nowadays the roles of \MIS{} teams' are to participate actively in
\SM{} building process and express their needs in this
project. We ask them what is information that they would like to on
\SM{}, what are the main features of tool that we will recommend
to manage system map.

Business teams are responsible to present and explain us process on
factory (business) side. They must tell us, if used application does
fit their need at present day and if they need to make some
changes. Another important point is the application's efficiency. It
means if the user uses majority of functions of application and if the
system offers all functions they need. Different business services
have some applications which are used very seldom, so we'd like to
know if they really have the profit of these systems, if another
system (already used in this business area) offers the same methods or
functions to execute this work.



%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{Supply information about system map's update}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\indent Here we discuss responsibilities and roles of each team in the
future. As we already mentioned today most of support teams have their
databases.  The major problem that they have is to maintain these
databases updated. With centralised solution of \SM{} it'll be
absolutely required that all teams contribute in update of
information.

We had a discussions with \MIS{} groups about the mode of update of
system map's database. Some of them preferred that each team have
access to database to update information concerning the systems they
are managing.

If we will work in this way we don't resolve the problem of
co-ordination, of data sharing. 

The model that we propose is to have a central person for each \MARS{}'s
site or couple of sites, who will be responsible of system map of the
site. The information source can be key user of application or \MIS{}
team, to have the best co-ordination between these two parts, the
right person could be Account Manager. This is the person who is
already situated among Business and IT. The account manager will be
informed about all changes on systems and he will co-ordinate the work
of local team, which will update in reality the application's or
infrastructure equipment's' landscape. To facilitate the work of
person who send information about update and also of person who'll
update the database, they will have typical form dedicated for this
job (not done yet).

	
